those are the winsw logs, you need the log file for netclient, which is in the directory

i since then moved on to DO droplets and started playing with NM. so far, liking the way it works. i just can’t get my AD DNS to work for ext clients. no netclient installed on the AD DNS servers. configured egress from a Linux machine inside my local network. can ping by IP but not by hostname/FQDN.

found this all the way at the bottom of the Netmaker Docs under "Configuring DNS for Ext Clients (OPTIONAL)" PORT_FORWARD_SERVICES="dns" --> PORT_FORWARD_SERVICES="" after changing this line, i'm able to ping FQDN using my AD DNS.

when configuring egress for 0.0.0.0/0, my vultr VM's public interface is showing as enp1s0. and this is the interface i used for egress and it will not work. modified /etc/default/grub with the line GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0". do "update-grub" and reboot VM. after the reboot, the interface now shows as eth0. and that somehow worked.

for OAuth, insert and change with your Oauth provider in docker-compose.yml. i inserted it after PORT_FORWARD_SERVICES: "" in the netmaker block. AUTH_PROVIDER: "" # "" CLIENT_ID: "" # "" CLIENT_SECRET: "" # "" SERVER_HTTP_HOST: "" # "api." FRONTEND_URL: "" # "https://dashboard." AZURE_TENANT: "" # "" OIDC_ISSUER: "" # https://oidc.yourprovider.com - URL of oidc provider

that's a big oops... i know i have a mix of EE and Community Edition running and the docker-compose.yml i modified to use Oauth is my EE server and i started getting emails from @netmaker.io about "Netmaker Pro - You have crossed your free trier limits." i converted it to Community Edition. modified docker-compose.yml and was able to get back in my server.

I'm experimenting with Netclient in LXD. Dreaded the red "ERROR" status on my nodes.